Issue & Reproduction Steps

When a process is exported and a screen or script is not found, dependencies are no longer searched for and an incomplete file is created

Solution

It prevents the search for dependencies from ending when a screen or script is not found, now it will continue searching for all dependencies.

How to Test

Create a process assign it screens, scripts then save it.
Go eliminate the screens and scripts in the database.
then without updating the screens and scripts in the export process.
It shouldn't cut the dependency lookup and create a file to export.

Related Tickets & Packages

• FOUR-9163

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

ci:deploy
ci:connector-send-email:bugfix/FOUR-9163
ci:package-webentry:bugfix/FOUR-9163
ci:connector-pdf-print:bugfix/FOUR-9163
ci:package-actions-by-email:bugfix/FOUR-9163